Here you can search through the pages of this Namespace, their attachments and the files uploaded to the system.
Note: the results will only display the items you have permissions to read.
Subscribing to Streaming Data The T4 FIX API provides (optional) subscriptions to streaming market data for all markets available in order routing. Market data is made available asynchronously and concurrently to order routing flow. The market data subscriptions are active during a FIX [...]
Describing Market Data The T4 FIX API supports streaming of market data with the Market Data Incremental Refresh message (Tag 35=X) alongside MarketData Snapshot messages (Tag 35=W). Market Data Incremental [...]
Describing Market Data The T4 FIX API support streaming of market data with the Market Data Snapshot message (Tag 35=W). The Market Data Snapshot messages are used as the response to a Market Data Request message. It [...]
If at anytime you require assistance from CTS you must send in your FIX messages to API@ctsfutures.com . Our API support will not answer if the messages aren't delimited in a reasonable way for readability Session Initiation After a successful SSL connection, the T4 FIX API basic requirement is to have both the Initiator and Acceptor start with sequence number 1. The client will initiate the FIX [...]
This document outlines how to use the T4 FIX API 4.0 of Cunningham Trading Systems (CTS). The T4 FIX API conforms to the Financial Information eXchange (FIX) Protocol with minor improvements and customizations as presented herein. T4 FIX API applications cannot be run simultaneously with our frontend or other [...]
Order State and Execution The Execution Report message (MsgType=8) is used by the T4 FIX API to electronically notify execution events and order state changes. The following areas are covered by the T4 FIX API Execution Reports: * Confirm the receipt of an order. * Confirm changes to an existing order (i.e. accept, cancel requests and cancel replace requests). * Relay order status changes. * Relay trade information [...]
Multiple Traders Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User. To enter Multi-Trader mode, the Master User must explicitly request it as an option on the FIX Logon with Tag 372 (RefMsgTypes) = UCG. Authentication Requirements [...]
Logon Traders Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User.
The FIX API responds to Trader Logons with the Trader Logon Response message. With this message, the FIX [...]
Logging out Traders Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User. A trader that has been successfully authenticated with a Trader Logon can be logged out by the Master User with a Trader Logout message. The FIX API [...]
Logging out Traders Under an established FIX Session, multiple traders/users can be authenticated with the Trader Logon message. Trader Logons allow order routing for multiple traders under the the same physical connection of the FIX Session. Trader Logons must follow the successful FIX Logon of the initial Master User. A trader that has been successfully authenticated with a Trader Logon can be logged out by the Master User with the Trader Logout message. Identifying the Trader The Trader Logout identifies [...]
[...] Requests To receive Security Definitions as responses to Security Definition Requests, the initiating FIX session Logon message must have Tag 372 (RefMsgType) set to "c" (i.e. Enable security definitions requests). Security definition requests that are not enabled will be rejected with a Security Definition containing a SecurityResponseType of Reject Security Proposal (Tag 323=5).
Definition of Securities The T4 FIX API provides a mechanism to list the securities available for [...]
The T4 FIX API conforms to the Financial Information eXchange (FIX) Protocol with minor improvements and customizations. Documentation on FIX can be found at http://www.fixprotocol.org .
Requirements
To develop to the T4 FIX API, you need a dedicated SSL connection to a T4 FIX API [...]
Application Management Beyond order routing, the T4 FIX API provides additional functionalities to query and manage positions, orders and accounts. The Collateral Inquiry message (MsgTyp=BB) is the cornerstone of (non-routing) application management. If the requests are successful, Collateral Inquiries result in responses from the T4 FIX API server with Execution Reports , Collateral Reports or Security Definitions [...]
Submitting New Orders The New Order Single message (MsgType=D) is used by the T4 FIX API to electronically submit orders to an exchange for execution. This message is used for all strategy types including outright futures, futures options, spreads and multileg strategies. The instrument for which the order is submitted is identified with the following tags: Tag 48 (SecurityID), Tag 55 (Symbol), Tag 207 (SecurityExchange) and Tag 167 (SecurityType). Options orders must also include the Strike Price (Tag 202) [...]
Amending Working Orders The Order Cancel-Replace Request message (MsgType=G) is used by the T4 FIX API to electronically amend (i.e. revise) the replaceable fields of working orders. This message is used for all CTS strategy types including outright futures, futures options, spreads and multileg strategies. The instrument (for which the replace applies) is identified with the following tags: Tag 48 (SecurityID), Tag 55 (Symbol) Tag 207 (SecurityExchange) and Tag 167 (SecurityType). Options orders must also [...]
[...] used to define the characteristics of exchanges, contracts and specific instruments (markets). The T4 FIX API returns this message as a result of queries performed with the Security Definition Request message. The Security definition message includes a complete description of securities by providing Exchange identifier, Contract identifier, Market identifier, pricing, minimum trading volumes, minimum price amount (including Variable Tick Tables), quantity leg ratios, buy/sell sides, [...]
[...] order and contingent Related orders. When a Spark order is submitted, the trigger order is sent to the market while the Related orders are suspended (held). When the trigger component is traded, the Related components are all activated and sent to the exchange to work independently of each other. The Spark's Related components are labeled with an Activation Type of Queue (Tag 10102=6). A Spark Order is submitted with the New Order List (Tag 35=E) message. Following are the most relevant tags to build a Spark order.
Tag 1385=3 ContingencyType Specifier of Spark order [...]
[...] is AutoOCO_P (Tag 1385=7), stop price must be entered as an absolute stop price.
Tag 48 SecurityID Market for which the order is sent
Tag 55 Symbol Contract for which the order is sent
Tag 207 SecurityExchange Exchange for which the order is sent
Please note:
The Volume for the two components of the OCO should be specified as 0. The T4 FIX API works out the required OCO volumes based on the trigger order. The Side for the OCO components is specified as the opposite of the [...]
[...] (Tag 900) - Margin Requirements (Tag 899) + Premium (Tag 901). This amount does not take into account (market-price-varying) unrealized P&L for positions open in the market. 3. Account Position Updates Account Position Updates carry detailed information on open positions, working orders and fills for traded markets within an account. This type of Collateral Report informs of portfolio composition as in the account's number of buys and sells (Tags 3002 and 3003), number of short and long positions (Tag 53), Open Volume (Tag 3011), etc. This [...]
Message Rejection FIX Session rule violations are manifested through the Reject message. The receipt of a Reject message signals a serious violation of FIX Session rules. Appropriate action must immediately be taken by the receiver of a Reject message. A rejected message may be retransmitted by the sending application if a correction is appropriate. The T4 FIX API can detect an extensive set of FIX session violations and [...]
Canceling Working Orders The Order Cancel Request message (MsgType=F) is used by the T4 FIX API to electronically cancel (i.e. pull) working orders. This message is used for all CTS strategy types including outright futures, futures options, spreads and multileg strategies. The instrument for which the cancel-request is submitted is identified with the following tags: Tag 48 (SecurityID), Tag 55 (Symbol) and Tag 207 (SecurityExchange). In addition to full market specification, [...]
[...] Orders with Multiple Components: Batch Orders The New Order List message (MsgType=E) is used by the T4 FIX API to electronically submit (multiple-component) orders to an exchange for execution. Orders with multiple components are also known as Batch Orders. They are identified by its Contingency Type (Tag 1385). Batch orders can only contain (constituent) orders. The New Order List is built by specifying its ContingencyType (Tag 1385), target instrument (Tags 48, 55, 207, 167), account (Tag 1) and by adding each [...]
Rejecting Market Data Requests The Market Data Request Reject (Tag 35=Y) is generated when the T4 FIX API cannot honor a Market Data Request. The rejection reason may stem from market or exchange not available, lack of user permission, undefined markets, etc. The rejection is paired against a previous
On Market Mode Activation Orders will be held (i.e. suspended) in the T4 FIX API server until the specific market mode event (as entered with the Activation Value - Tag 10103) occurs. At this activation point, the order is released to the exchange. An Activation Order is entered with the New Order Single (Tag 35=D) message. Following are the most relevant tags to build an On Market Mode Activation Order.
Tag 10102=4 Activation [...]
A Flatten order can be used to flatten a current position regardless of what that position is. The T4 FIX API server figures out the volume and Buy/Sell parameters. If a position does not currently exist for the SecurityID (Tag 48) of the submitted flatten order, the order is rejected. A Flatten Order is entered with the New Order Single (Tag 35=D) message. Following are the most relevant tags to build a Flatten order.
Tag 40=F OrdType Specifier of Flatten Order Type
Tag 38 OrderQty Set to 0 to have [...]
A MarketIfTouched (MIT) Order is submitted to T4 FIX API server to suspend and await subsequent exchange submittal when a trigger price is hit. Once a trade occurs at the trigger price, the T4 FIX API server releases (to the exchange) the MarketIfTouched Order as a Market Order (Tag 40=0). A MarketIfTouched Order is entered with the New Order Single (Tag 35=D) message. Following are the most relevant [...]
Requesting the Status of an Order The Order Status Request message (MsgType=H) is used by FIX API clients to electronically interrogate the instantaneous state of an order. The OrderId Tag (37) identifies the specific order for which the Order Status Request is submitted. To pinpoint the order's instrument, the SecurityID (Tag 48) and Side (Tag 54) must also be specified. From the client's perspective, the queried order can further be identified with a verbose (# characters >= 12 and The Order Status Request message is responded to [...]
[...] (administrative or application) are preceded by a Standard Header. In addition to providing the identification of FIX Session participants, the Standard Header identifies the Message Type (Tag 35), Message Length (Tag 9), Origination times (Tag 52 and Tag 122) and Message Sequence order (Tag 34). The Standard Header also offers additional information on FIX Session authentication, resent messages, duplicated messages and message routing and delivery. Standard Header Dictionary
Tag Field Name Req'd Comments 8 BeginString Y FIX.4.2 [...]
An OCO (One Cancels Other or Order Cancels Order) consists of a buy limit order below the market and a buy stop order above the market, or a sell limit order above the market and a sell stop order below the market. When one gets filled the other is cancelled. If one is partially filled then the volume on the other is reduced accordingly. An OCO Order is submitted with the New Order List (Tag 35=E) message. Following are the most relevant tags to build an OCO order.
Tag 1385=1 [...]
[...] Rejecting Attempts to Amend or Cancel Orders The Order Cancel Reject message (MsgType=9) is used by the T4 FIX API to electronically reject (failed) attempts to cancel or replace an order. Cancel Rejects are only generated for unsuccessful client side Order Cancel Request , Order Cancel Request or List Cancel Request messages. Unsolicited Cancel Rejects may also be generated for cancel rejects originated from non-T4-FIX-API [...]